Storage Module and Host Device for Storage Module Defragmentation

ABSTRACT

A storage module and host device for storage module defragmentation are disclosed. In one embodiment, a host controller sends a storage module a first set of logical block addresses of a file stored in the storage module. The host controller receives a metric from the storage module indicative of a fragmentation level of the file in physical blocks of memory in the storage module. If the metric is greater than a threshold, the host controller reads the file and then writes it back to the storage module using a different set of logical block addresses. To avoid sending the file back and forth, in another embodiment, the host controller sends the fragmentation threshold and the different set of logical block addresses to the storage module. The storage module then moves the file itself if the metric indicative of the fragmentation level is greater than the threshold. Other embodiments are provided.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. provisional patent application no. 61/936,170, filed Feb. 5, 2014, which is hereby incorporated by reference.

BACKGROUND

Fragmentation of files due to host fragmentation or storage module fragmentation can degrade system performance. With host fragmentation, files are scattered across many non-consecutive logical block address (LBA) ranges of the storage module. So, the more LBA ranges are used to store a file, the more fragmented the file becomes. Further, in some file systems, such as EXT4, the file allocation table (FAT) is mixed with stored data. Reading a fragmented file in such a system requires more operations, as the structure of the file is more complicated. This can degrade read performance.

With storage module fragmentation, files are scattered among many physical blocks in memory. The more physical blocks that are allocated for the same file, the more fragmented the file is. Because a fragmented file often does not occupy the entire physical block, a physical block that stores part of a fragmented file will often store data of other files. So, when a host deletes a file that is fragmented over several physical blocks, this may result in fewer free blocks than intended, as the blocks still hold data for other files. Because such a file deletion will leave “holes” of free space in an otherwise-occupied physical block, the storage module will need to perform several “housekeeping” operations to create a free block, which can degrade system performance.

Additionally, in some environments, such as in mobile computing systems, when a file is fragmented by the storage module, the host does not know how fragmented the file is, so it does not know what action is needed to attempt to defragment the file. Further, while a host is aware of the host-fragmentation problem and can attempt to solve it by moving a scattered file to consecutive LBA ranges, such moving can actually degrade performance because of the storage fragmentation problem.

Overview

Embodiments of the present invention are defined by the claims, and nothing in this section should be taken as a limitation on those claims.

By way of introduction, various embodiments relate to a storage module and host device for storage module defragmentation. In one embodiment, a host controller sends a storage module a first set of logical block addresses of a file stored in the storage module. The host controller receives a metric from the storage module indicative of a fragmentation level of the file in physicals blocks of memory in the storage module. If the metric is greater than a threshold, the host controller reads the file and then writes it back to the storage module using a different set of logical block addresses. To avoid sending the file back and forth, in another embodiment, the host controller sends the fragmentation threshold and the different set of logical block addresses to the storage module. The storage module then moves the file itself if the metric indicative of the fragmentation level is greater than the threshold. To perform this embodiment on a plurality of files, the host controller can send the information about the files on a file-by-file basis to the storage module or can send the information as a group to the storage module. In another embodiment, a host controller sends, to the storage module, a set of logical block addresses of a file stored in the storage module, and the storage module generates, and sends to the host controller, a metric indicative of a level of fragmentation level of the file in physical blocks of memory in the storage module. In yet another embodiment, a host controller reads a file stored in a storage module and writes it back to the storage module according to a specified writing mode.

Other embodiments are possible, and each of the embodiments can be used alone or together in combination. Accordingly, various embodiments will now be described with reference to the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary storage module of an embodiment.

FIG. 2A is a block diagram of a host of an embodiment, where the exemplary storage module of FIG. 1 is embedded in the host.

FIG. 2B is a block diagram of the exemplary storage module of FIG. 1 removably connected to a host, where the storage module and host are separable, removable devices.

FIGS. 3A and 3B illustrate a storage module fragmentation problem of an embodiment.

FIG. 4 is a flow chart of an embodiment for providing a host with information about storage module fragmentation and for reducing the fragmentation of a file.

FIG. 5 is a flow chart of a method of an embodiment for reducing the fragmentation of a file without transferring the file between a storage module and a host.

FIG. 6 is a flow chart of another method of an embodiment for reducing the fragmentation of a file without transferring the file between a storage module and a host.

FIG. 7 is a chart summarizing various embodiments.

FIG. 8 is a flow chart of a method of an embodiment for a defragmentation technique that can be used with storage modules following the NVMe protocol.

FIG. 9 is an illustration of an embodiment for writing files in a multiple queue environment.

FIG. 10 is an illustration of an embodiment for writing files in a multiple queue environment when a defragmentation technique is used.

DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EMBODIMENTS

As mentioned above, a host typically does not know how fragmented a file is in physical blocks of memory in the storage module, so it does not know what action is needed to attempt to defragment the file. The following embodiments can be used to address the storage module fragmentation problem discussed above by giving the host an understanding of storage module fragmentation and providing the host with a set of tools to handle storage device fragmentation with various levels of involvement. Before turning to these and other embodiments, the following paragraphs provide a discussion of an exemplary storage module and host that can be used with these embodiments. Of course, these are just examples, and other suitable types of storage modules can be used.

As illustrated in FIG. 1, a storage module 100 of one embodiment comprises a storage controller 110 and non-volatile memory 120 (here, one or more NAND memory die, although other type of memory technology can be used). The storage controller 110 comprises a memory interface 111 (a Flash Interface Module) for interfacing with the non-volatile memory 120 and a host interface module 112 for placing the storage module 100 operatively in communication with a host controller 245. As used herein, operatively in communication with could mean directly in communication with or indirectly in communication with through one or more components, which may or may not be shown or described herein, in a wired or wireless fashion. FIG. 1 also shows the storage module 100 in communication with a host 240 via a storage device interface using a storage protocol such as, for example, eMMC, UFS, PCI Express, DDR-3/4, or SATA. The host 240 comprises applications 250, a file system 260, a driver 270, and a memory (e.g., RAM) 280, although other or different components can be used. Also, as mentioned above, the host 240 contains a host controller 245, and it should be understood that actions taken by the host with respect to the storage module 100 can be performed using the host controller 245. Different storage module—host configurations can be used, as shown in FIGS. 2A and 2B.

As shown in FIG. 2A, the storage module 100 can be embedded in a host 210 having a host controller 220. That is, the host 210 embodies the host controller 220 and the storage module 100, such that the host controller 220 interfaces with the embedded storage module 100 to manage its operations. (It should be noted that while the host controller 220 can control the storage module 100, the storage module 100 can have its own controller to control its internal memory operations.) For example, the storage module 100 can take the form of an iNANDTM eSD/eMMC embedded flash drive by SanDisk Corporation, or, more generally, any type of solid state drive (SSD), a hybrid storage device (having both a hard disk drive and a solid state drive), and a memory caching system,. The host controller 220 can interface with the embedded storage module 100 using, for example, an eMMC host interface or a UFS interface. The host 210 can take any form, such as, but not limited to, a mobile phone, a tablet computer, a digital media player, a game device, a personal digital assistant (PDA), a mobile (e.g., notebook, laptop) personal computer (PC), or a book reader. As shown in FIG. 2A, the host 210 can include optional other functionality modules 230. For example, if the host 210 is a mobile phone, the other functionality modules 230 can include hardware and/or software components to make and place telephone calls. As another example, if the host 210 has network connectivity capabilities, the other functionality modules 230 can include a network interface. Of course, these are just some examples, and other implementations can be used. Also, the host 210 can include other components (e.g., an audio output, input-output ports, etc.) that are not shown in FIG. 2A to simplify the drawing.

As shown in FIG. 2B, instead of being an embedded device in a host, the storage module 100 can have physical and electrical connectors that allow the storage module 100 to be removably connected to a host 240 (having a host controller 245) via mating connectors. As such, the storage module 100 is a separate device from (and is not embedded in) the host 240. In this example, the storage module 100 can be a handheld, removable memory device, such as a Secure Digital (SD) memory card, a microSD memory card, a Compact Flash (CF) memory card, or a universal serial bus (USB) device (with a USB interface to the host), and the host 240 is a separate device, such as a mobile phone, a tablet computer, a digital media player, a game device, a personal digital assistant (PDA), a mobile (e.g., notebook, laptop) personal computer (PC), or a book reader, for example.

In FIGS. 2A and 2B, the storage module 100 is in communication with a host controller 220 or host 240 via the host interface module 112 shown in FIG. 1. The host interface module 112 can take any suitable form, such as, but not limited to, an eMMC host interface, a UFS interface, and a USB interface. The host interface module 110 in the storage module 110 conveys memory management commands from the host controller 220 (FIG. 2A) or host 240 (FIG. 2B) to the storage controller 110, and also conveys memory responses from the storage controller 110 to the host controller 220 (FIG. 2A) or host 240 (FIG. 2B). Also, it should be noted that when the storage module 100 is embedded in the host 210, some or all of the functions described herein as being performed by the storage controller 110 in the storage module 100 can instead be performed by the host controller 220.

Returning to FIG. 1, the storage controller 110 comprises a flash management module 113, which can contain a central processing unit (CPU) 113 running software and/or hardware modules to manage the memory 120 (e.g., performing logical-to-physical address mapping, etc.). The storage controller 110 can be implemented in any suitable manner. For example, the storage controller 110 can take the form of a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, for example. Suitable controllers can be obtained from SanDisk or other vendors. The storage controller 110 can be configured with hardware and/or software to perform the various functions described below and shown in the flow charts.

The non-volatile memory 120 can also take any suitable form. For example, in one embodiment, the non-volatile memory 120 takes the form of a solid-state (e.g., flash) memory and can be one-time programmable, few-time programmable, or many-time programmable. The non-volatile memory 120 can also use single-level cell (SLC), multiple-level cell (MLC), triple-level cell (TLC), or other memory technologies, now known or later developed. Also, the non-volatile memory 120 can be a two-dimensional memory or a three-dimensional memory.

As mentioned above, a host typically does not know how fragmented a file is in physical blocks of memory in the storage module, so it does not know what action is needed to attempt to defragment the file. FIGS. 3A and 3B illustrate the storage module fragmentation problem. In FIG. 3A, there are four physical blocks of memory, and three files stored therein. The squares denote the smallest writing units. File A is contained in blocks 0 and 1, File B is contained entirely in block 1 (with some free space available in block 1), and File C in contained entirely in block 3 (with no free space available). Block 2 is completely empty. FIG. 3B shows the storage of the same three files identical in size, but, this time, the storage of these files is more fragmented. Specifically, parts of all four files are stored in each of the blocks. The following embodiments can be used by a host to address storage module fragmentation.

Typically, a host does not have insight into the level of storage module fragmentation. So, in one embodiment, a new communication between the host 240 and storage module 100 is provided. This will be illustrated in conjunction with the flow chart 400 of FIG. 4. As shown in FIG. 4, the host 240 prepares a list of files for defragmentation (act 410) and goes through this list of files on a file-by-file basis (acts 420, 430). For each file, the host 240 sends a query command to the storage module 100 with the logical block address (LBA) ranges of the file (act 440). In response to this query, the storage module 100 provides the host 240 with a defragmentation metric for the file (act 450). That is, the defragmentation metric is part of a response to the query command (this embodiment assumes a storage protocol is used in which for every command, there is a response.)

As used herein, a defragmentation metric reflects the level of fragmentation for a file, and its value relates to the degree of such fragmentation. An example of a defragmentation metric can include the number of physical blocks containing the file. So, in the example shown in FIG. 3A, the fragmentation metric is two blocks for file A, one block for file B, and one block for file C. In contrast, in the more-fragmented example shown in FIG. 3B, the fragmentation metric is four blocks for file A, two blocks for file B, and four blocks for file C. Of course, the number of physical blocks containing a file is just one example of a defragmentation metric. Other examples include, but are not limited to, a hot/cold indication, and a mapping efficiency indication. A hot/cold indication describes how long ago the data was written. For example, a file written a year ago can be considered cold, whereas a file written five minutes ago can be considered hot. From the storage module's point of view, it would be preferred to perform fragmentation on cold files before hot files since hot files still might be changed by the host. Mapping efficiency describes the amount of excessive reads from management tables that are required in order to find a physical location. This metric refers to the fact that flash management software contains one or more tables mapping logical addresses to physical address. When the mapping unit is very small (e.g., 4 KB), the logical-to-physical table (L2P) of a typical storage (e.g., 32 GB) can be very large (e.g., 8 MB). For practical reasons such as cost and power, this table is not stored in the RAM of the storage controller 110 and has to be written to the NAND memory dies 120. The L2P table can be scattered among several NAND memory dies, and, within each die, parts of the tables can be in different blocks and pages. In some situations of storage fragmentation, not only is the data fragmented, but the L2P table(s) are fragmented as well. In this case, reading the file will involve additional reads from the L2P table before reading/writing the data. These additional “control” reads degrade the storage performance.

Based on the received defragmentation metric, the host 240 can choose to take various actions. For example, as shown in FIG. 4, the host 240 can determine whether the received defragmentation metric meets an expectation (e.g., greater than a predetermined or dynamic threshold) (act 460). If the metric meets the expectation (such as file A in FIG. 3A), the host 240 can inquire about the next file (acts 420 et seq.). However, if the metric does not meet the expectation (such as file A in FIG. 3B), the host 240 can move the file to another location in the memory 120 of the storage module 100 to decrease fragmentation of the file. To do this, the host 240 can read the file from the existing physical block into memory in the host 240 (e.g., the host's RAM 280 or other volatile or non-volatile memory in the host 240) (act 470). Then, the host 240 writes the file back to the storage module 100 using a new file command (act 480), so that the file will occupy fewer physical blocks (or, ideally, with minimal storage fragmentation). To do this, the host can send a list of LBAs reflecting one new file (preferably, one consecutive range of LBAs). The host 240 can then also instruct the storage module 100 as to the writing mode. For example, the host 240 can instruct the storage module 100 to write in a “best effort mode,” in which the storage module tries writing the file to a minimal number of physical blocks but without any guarantee. Along with this type of write mode, the host 240 can provide the storage module 100 with information about the file type (e.g., log, temp, JPG, OS), and the storage module 100 can determine what best effort should be made for that file type. For example, the storage module 100 may make a better effort trying to write an OS file than a log file. Alternatively, the host 240 can instruct the storage module 100 to write in a “warranted mode,” in which the storage module 100 shall perform any housekeeping required before writing to assure minimal number of physical blocks. In either mode, after the file has been written, the storage module 100 can return the fragmentation metric for the new file to the host 240. The host 240 can use this metric to see if the result of a “best effort” write was satisfactory. If it was not, the host 240 can reissue the write as a “warranted” write.

The following chart is a high-level description of the commands and response arguments for the embodiment discussed above. Of course, this is merely one example, and other arguments can be used.

Command Name Command Arguments Response Arguments Query CMD - Number of LBA ranges; N Fragmentation metric #1 query of existing LBA range #1: . . . file command (start LBA, end LBA) Fragmentation metric #K . . . LBA range #N: (start LBA, end LBA) New file CMD - Number of LBA ranges; N Fragmentation metric #1 writing new file LBA range #1: . . . command in a (start LBA, end LBA) Fragmentation metric #K defragmented . . . way LBA range #N: (start LBA, end LBA) Mode (e.g., best effort or warranted) File type (e.g., log, temp., JPG, OS)

As can be seen by the above examples, this embodiment allows the host 240 to have visibility into the storage module fragmentation for a given file and provides the host 240 with a set of tools to handle storage device fragmentation with various levels of involvement. For example, the host 240 can read and write the file back to the storage module 100 with a better fragmentation metric (e.g., fewer number of physical blocks), if desired. In another embodiment, instead of the host 240 reading the file out of the storage module 100 and then writing the file back to the storage module 100, this defragmentation process is performed without moving the file back and forth between the storage module 100 and the host 240, thereby avoiding the data transfer on the bus. FIG. 5 is a flow chart 500 that illustrates this embodiment. As shown in FIG. 5, the host 240 prepares a list of files for defragmentation (act 510) and goes through this list of files on a file-by-file basis (acts 520, 530). For each file, the host 240 provides a list of LBA ranges reflecting the current storage of the file, as well as a potential new list of LBA ranges for the new location of the file (act 540). The storage module 100 then moves the data of the file to a smaller number (preferably, the minimal number) of physical blocks and confirms the mapping of new LBA ranges. The host 240 can also provide the metric expectation, so the storage module 100 can determine whether or not to perform the defrag operation, as well as the write mode (e.g., best effort (along with optional file type) or warranted), if the defrag operation is to be performed. Optionally, the storage module 100 can first respond with the estimated fragmentation metric for the new and old ranges to allow the host 240 to approve the fragmentation before it takes place (based on comparing the old and new metrics).

The advantage of this embodiment over the previous embodiment is that the host implementation is simpler because the transfer of unnecessary data on host-storage bus is eliminated. In this case, the file system on the host 240 has the knowledge on each file, and it sends a Defrag File command one by one. The following chart is a high-level description of the commands and response arguments for this embodiment. Of course, this is merely one example, and other arguments can be used.

Command Name Command Arguments Response Arguments Defrag One File Existing LBA ranges of the Completion status CMD - defrag of file New LBA ranges Fragmentation metric #1 existing file (if desired to be . . . command different from existing) Fragmentation metric #K Mode (e.g., best effort or warranted) Metric expectation File type (e.g., log, temp., JPG, OS)

Further optimization can be achieved if the host 240 sends list of files or a directory, with the host 240 optionally providing priorities and scheduling information. This embodiment is shown in the flow chart 600 of FIG. 6 and provides a more efficient operation that the one discussed above. As shown in FIG. 6, the host 240 prepares a list of files for defragmentation (optionally, with a priority list) (act 610) and then sends a defrag file database command to the storage module 100 (act 620). The storage module 100 parses the data base and plans the defragmentation process accordingly. During long idle times (e.g., at night time with the host (e.g., phone) is charging), the storage module 100 can perform defragmentation on the whole list of files according to the priority required by the host 340 and according to new and old metrics.

Irrespective of whether the host 240 communicates the files on a file-by-file basis (FIG. 5) or as a list/database (FIG. 6), the defragmentation operations of either method can be executed in a synchronic (blocking) or a synchronic (non-blocking) mode. In the synchronic mode, the storage module 100 will execute the command in the foreground and will release the busy signal only after finishing all the required operation. In contrast, in the asynchrony mode, the storage module 100 will keep the command in a non-volatile mode and will release the busy signal immediately. The executing of the command will be done in the background, preferably during idle time (e.g., during night time). The progress of executing can be communicated through a set of registers in the storage module 100 that the host 240 can poll.

The following chart is a high-level description of the commands and response arguments for this embodiment. Of course, this is merely one example, and other arguments can be used.

Command Name Command Arguments Response Arguments Defrag File DB List of files, each has Completion status CMD - defrag list the following: Fragmentation metric #1 of files command LBA ranges . . . File type (e.g., log, temp., Fragmentation metric #K JPG, OS) Mode (e.g., best effort or warranted) Priority Metric threshold

FIG. 7 is a chart that summarizes the relationships between the embodiments discussed above.

There are many alternatives that can be used with these embodiments. For example, in addition to or instead of moving the file to reduce storage device fragmentation, the host 340 can also use the received defragmentation metric to decide whether to activate host defragmentation. Unlike storage module fragmentation which focuses on physical blocks in the memory 120 of the storage module 100, host fragmentation focuses on the logical block address (LBA) ranges of a file. A host can address this problem by moving a scattered file to consecutive LBA ranges. However, if the file is fragmented across many physical blocks, host defragmentation can actually lead to worse performance than if the LBA ranges of the file were left as-is. So, by using this embodiment, the host 240 can base the determination of whether to perform host defragmentation on the storage module defragmentation metric.

In another embodiment, the defragmentation techniques discussed herein can be used with storage modules using the NVM Express (NVMe) protocol. Such storage modules can benefit from these embodiments by leveraging data set management commands that allow the host 240 to indicate to the storage module 100 when multiple non-consecutive LBA ranges are part of the same file. This uses the DATASET MANAGEMENT command and the Integral Read flag of the WRITE command in NVMe protocol. This embodiment will be discussed in more detail in conjunction with the flow chart 800 of FIG. 8, which describes a partial file write (or file update) using NVMe commands from the point of view of the host 240, in which the above embodiments are utilized on the storage module 100 side in order to offer improved performance.

As shown in the flow chart 800, the host 240 first determines that a write is to a partial or complete file (act 810). The host 240 then allocates or updates the allocation of an LBA range in the file system (act 820). Next, the host 240 performs a loop for each contiguous range of LBAs (“extent”) (act 830). First, the host 240 determines whether there is new data written to the extent (act 840). If there isn't, the host 240 submits a data set management command with an integral read flag (IDR) for the extent LBA range (act 850). If there is, the host 240 submits a write command with an IDR flag for the extent LBA range (act 860). When the end of the file occurs (act 870), the storage module 100 consolidates blocks and completes the command (act 880). In this embodiment, the storage module 100 consolidates blocks as per the above embodiments before completing the dataset management commands issued by the host 240. The host 240 thus knows that the file is stored optimally.

A variation of this involves new file writes. Typically, new writes are programmed to the next available free block without regard for whether the following writes are part of the same sequence. When multiple files are written simultaneously using multiple queues, this can lead to the write interleaving shown in FIG. 9. In FIG. 9, the swap and temp queues (3 and 4) have write blocks interleaved with two files (F1 and F2). Each resulting page contains elements of multiple content types. (one represents existing content associated with file F1, and another represents existing content associated with F2.). By use of the consolidation technique discussed above, the storage module 100 can have a priori knowledge of the extent sequences of F1 and F2 since existing blocks belonging to the same LBA ranges have been marked as integrally written or consolidated. After consolidation, the resulting block allocation scheme can look like what is shown in FIG. 10. If this is done during the copy itself, storage module performance will suffer during the write process, since consolidation will have occurred during an I/O command. Thus, the storage module 100 may defer the consolidation until after the write completes, based on the data set management hints received during the write. Furthermore, the host 240 may send data set management commands to the given range after a write completes and achieve the same effect.

During a host-driven defragmentation cycle (as described above), the host 240 may send a data set management range table with the integral read flag in order to trigger consolidation. Typical SSDs can contain thousands of files, making sending individual data set management commands clumsy and inefficient. In another embodiment, the host 240 sends a command to the storage module 100 indicating LBA ranges that already contain extent lists that map to individual files (as is common in file systems). The storage module 100 then parses these extent lists and consolidates the files accordingly. The foimat of the extent list may match the structures found in file systems (such as FAT, NTFS, and HFS+) that utilize extent lists for fragmented files. The storage module 100 does not update the extent list autonomously but rather reorganizes the physical blocks indicated by the LBAs in each extent such that they are not physically fragmented.

It should be noted that in a highly-asynchronous protocol like NVMe and with the large number of fragmented extents found in a typical SSD, it may be easier for the storage module to just make the determination of fragmentation level of each file without informing the host of each file's fragmentation level. However, both the technique of reporting metrics back to the host prior to defrag and the technique of sending a hint on a specific sequence of extents can be used.

It is intended that the foregoing detailed description be understood as an illustration of selected forms that the invention can take and not as a definition of the invention. It is only the following claims, including all equivalents, that are intended CO define the scope of the claimed invention. Finally, it should be noted that any aspect of any of the preferred embodiments described herein can be used alone or in combination with one another. 

What is claimed is:
 1. A storage module comprising: a memory; and a storage controller operatively in communication with the memory, wherein the storage controller is configure to: receive, from the host controller, a first set of logical block addresses of a file stored in the storage module, a second set of logical block addresses for a new location of the file, and a fragmentation threshold; determine a metric indicative of a fragmentation level of the file in physical blocks of memory in the storage module; determine whether the metric is greater than a threshold; and in response to determining that the metric is greater than the threshold, write the file to the second set of logical block addresses.
 2. The storage module of claim 1, wherein the storage controller is further configured to receive an instruction from the host controller as to what writing mode to use to write the file.
 3. The storage module of claim 2, wherein the writing mode comprises a best effort mode, in which the storage module makes its best effort to write the file using a minimum number of physical blocks.
 4. The storage module of claim 3, wherein the storage controller is further configured to receive an indication of a type of the file from the host controller, wherein an effort the storage module makes to write the file is based on the type of file.
 5. The storage module of claim 2, wherein the writing mode comprises a warranted mode in which the storage module must write the file using a minimum number of physical blocks.
 6. The storage module of claim 1, wherein the storage controller is further configured to: send a metric indicative of a level of fragmentation of the file written to the second set of logical block addresses.
 7. The storage module of claim 1, wherein the metric comprises a number of physical blocks in the storage module containing the file.
 8. The storage module of claim 1, wherein the metric comprises a hot/cold indication.
 9. The storage module of claim 1, wherein the metric comprises a mapping efficiency indication.
 10. The storage module of claim 1, wherein the storage controller is further configured to repeat the method for a plurality of files, wherein the sets of logical block addresses for the files are received on an individual basis from the host controller.
 11. The storage module of claim 1, wherein the storage controller is further configured to repeat the method for a plurality of files, wherein the sets of logical block addresses for the files are received in a group from the host controller.
 12. The storage module of claim 1, wherein the storage controller is further configured to: receive an indication from the host controller that multiple non-consecutive logical block address ranges are part of a same file.
 13. The storage module of claim 12, wherein the indication that multiple non-consecutive logical block address ranges are part of the same file comprises a dataset management command.
 14. The storage module of claim 12, wherein the indication that multiple non-consecutive logical block address ranges are part of the same file comprises an integral read flag.
 15. The storage module of claim 1, wherein the memory of the storage module is a three-dimensional memory.
 16. The storage module of claim 1, wherein the storage module is embedded in a host containing the host controller.
 17. The storage module of claim 1, wherein the storage module is removably connected to a host containing the host controller.
 18. The storage module of claim 1, wherein the storage module is a solid-state drive.
 19. A method for storage module defragmentation, the method comprising: performing the following in a storage module operatively in communication with a host controller: receiving, from the host controller, a first set of logical block addresses of a file stored in the storage module, a second set of logical block addresses for a new location of the file, and a fragmentation threshold; dete mining a metric indicative of a fragmentation level of the file in physical blocks of memory in the storage module; determining whether the metric is greater than a threshold; and in response to determining that the metric is greater than the threshold, writing the file to the second set of logical block addresses.
 20. The method of claim 19 further comprising receiving an instruction from the host controller as to what writing mode to use to write the file.
 21. The method of claim 20, wherein the writing mode comprises a best effort mode, in which the storage module makes its best effort to write the file using a minimum number of physical blocks.
 22. The method of claim 21 further comprising receiving an indication of a type of the file from the host controller, wherein an effort the storage module makes to write the file is based on the type of file.
 23. The method of claim 20, wherein the writing mode comprises a warranted mode in which the storage module must write the file using a minimum number of physical blocks.
 24. The method of claim 19 further comprising: sending a metric indicative of a level of fragmentation of the file written to the second set of logical block addresses.
 25. The method of claim 19, wherein the metric comprises a number of physical blocks in the storage module containing the file.
 26. The method of claim 19, wherein the metric comprises a hot/cold indication.
 27. The method of claim 19, wherein the metric comprises a mapping efficiency indication.
 28. The method of claim 19 further comprising repeating the method for a plurality of files, wherein the sets of logical block addresses for the files are received on an individual basis from the host controller.
 29. The method of claim 19 further comprising repeating the method for a plurality of files, wherein the sets of logical block addresses for the files are received in a group from the host controller.
 30. The method of claim 19 further comprising: receiving an indication from the host controller that multiple non-consecutive logical block address ranges are part of a same file.
 31. The method of claim 30, wherein the indication that multiple non-consecutive logical block address ranges are part of the same file comprises a dataset management command.
 32. The method of claim 30, wherein the indication that multiple non-consecutive logical block address ranges are part of the same file comprises an integral read flag.
 33. The method of claim 19, wherein the memory of the storage module is a three-dimensional memory.
 34. The method of claim 19, wherein the storage module is embedded in a host containing the host controller.
 35. The method of claim 19, wherein the storage module is removably connected to a host containing the host controller.
 36. The method of claim 19, wherein the storage module is a solid-state drive. 